Bump @vscode/windows-process-tree from ^0.6.0 to ^0.7.0 in both root and remote package.json.#307205
Bump @vscode/windows-process-tree from ^0.6.0 to ^0.7.0 in both root and remote package.json.#307205ZA139 wants to merge 3 commits intomicrosoft:mainfrom
@vscode/windows-process-tree from ^0.6.0 to ^0.7.0 in both root and remote package.json.#307205Conversation
|
I have reverted the changes to The version bump is now only reflected in |
|
Hi @justschen , just checking in on the status of this PR. Is there anything else needed from my side to move this forward? Thanks! |
|
Hi @rchiodo, @rzhao271, @justschen, I’ve submitted the PR to bump vscode’s windows-process-tree version from ^0.6.0 to ^0.7.0, as we discussed earlier. Thanks again for your review and guidance! |
|
Adding a note to bump this dependency tomorrow or Wednesday. Closing the PR for now because it will require lockfile updates from a team member to get through. |
@rzhao271 Understood. Thanks for taking care of the lockfile updates and the follow-up! Looking forward to seeing it merged. |
4 participants
Motivation
As WMIC has been deprecated, the Python Debugger extension's process attach feature needs the
getAllProcessesAPI (added in 0.7.0) to retrieve process name and command line in a single call, replacing the legacy WMIC-based approach.The extension includes a fallback mechanism — if
getAllProcessesis unavailable or fails (e.g. on older VS Code versions still shipping 0.6.x), it falls back to WMIC. So existing users are not affected.Related PRs:
Changes
package.json:@vscode/windows-process-tree^0.6.0→^0.7.0remote/package.json:@vscode/windows-process-tree^0.6.0→^0.7.0package-lock.json/remote/package-lock.json: updated accordinglyNote on package-lock.json (cpu-features)